Add stable mod logging API - #15

Summary

• add a versioned C ABI for host services and a Rust adapter that keeps mods on the standard log macros
• route mod records through loader-owned contexts for trusted attribution, centralized formatting, filtering, and output
• add Modloader/config/logging.json with default and per-mod levels, including off
• replace the Rust-ABI setup_logger lookup without preventing older mods from loading
• update proxygen to the modern fork and clean up current Rust ABI/compiler warnings
• add locked Windows CI that checks, tests, builds bass.dll, and uploads it as a workflow artifact without publishing releases

Compatibility

• old mods still load under the new loader but do not receive host logging
• new mods still load under old loaders but do not have their logging bridge installed
• the FFI surface uses only repr(C) records, fixed numeric values, pointers/lengths, and extern "C" callbacks

Verification

• cargo check --workspace --tests --locked --target x86_64-pc-windows-msvc
• cargo test --locked -p highfleet-mod-api --target aarch64-apple-darwin
• cargo clippy --locked -p highfleet-mod-api --target aarch64-apple-darwin --all-targets -- -D warnings
• host routing, formatting, and configuration tests passed in an isolated host-compatible harness
• Highfleet QOL release checks passed for both 1_151 and 1_163 using the new bridge